Dynamic adaptation of a configuration to a system environment

ABSTRACT

A method and apparatus for dynamic adaptation of a configuration to a system environment. An embodiment of a method includes obtaining system information for a system. The system information is stored in a memory. A setting of an abstract configuration for the system is resolved, with the resolution of the setting being based at least in part on the system information.

TECHNICAL FIELD

Embodiments of the invention generally relate to the field of computersystems and, more particularly, to a method and apparatus for dynamicadaptation of a configuration to a system environment.

BACKGROUND

In complex computer systems, the development of a configuration for eachparticular computer environment can be difficult, and is often a matterof experimentation and guesswork to develop a working model. Because acomplex system may include many disparate environments, this generallyrequires repeating the development process numerous times as varioussystems in different locations are configured.

If a configuration is developed for a system and is found to operateeffectively, this generally is of little help for other systems. In aconventional operation, a developer or user may wish to copy aconfiguration over to another system or to develop a configuration foruse in multiple systems, but this is generally not possible because ofsystem dependencies built into the configuration. Certain elements ofthe configuration will depend on the characteristics of the individualcomputer systems that are configured, and such characteristics willgenerally be different for each system that is encountered.

A conventional system configuration is static, and thus is not adaptableto new environments. If a developer or user wishes to copy a workingconfiguration for one system to another system or to develop aconfiguration for use in multiple computer systems, it is necessary toidentify all system dependent configuration elements, to determine howthe system dependent configuration elements need to be set to operate ineach system, and then to set these configuration elements. Thus, thetransfer of a configuration from one system to another is atime-consuming process, and the effort required to correct problemsseverely limits any advantage that might be gained in copying systemconfigurations or attempting to a common configuration for multipledifferent systems.

In order to form a conventional configuration process, the elements ofthe environment need to be placed into the configuration by a systemadministrator or other person. The process is generally done “by hand”because the required data for the configuration needs to be determinedfrom the system that will receive the configuration, the determined datarequires translation into the necessary form for the configuration, andthe resulting values must be installed in the correct configurationelements. As a result, the actual formation of the configuration is acomplex process.

SUMMARY OF THE INVENTION

A method and apparatus for dynamic adaptation of a configuration to asystem environment are described.

In one aspect of the invention, a method includes obtaining systeminformation for a system. The system information is stored in a memory.A setting of an abstract configuration for the system is resolved, withthe resolution of the setting being based at least in part on the systeminformation.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are illustrated by way of example, and notby way of limitation, in the figures of the accompanying drawings inwhich like reference numerals refer to similar elements.

FIG. 1 is an illustration of the transfer of a configuration in anembodiment of the invention;

FIG. 2 is an illustration of an embodiment of a system for generation ofa configuration;

FIG. 3 is an illustration of an embodiment of configuration development;

FIG. 4 is an illustration of an embodiment of configuration development;

FIG. 5 is a flowchart to illustrate an embodiment of configurationgeneration; and

FIG. 6 is an illustration of an embodiment of dynamic adaptation of aconfiguration to a system environment.

DETAILED DESCRIPTION

Embodiments of the invention are generally directed to a method andapparatus for dynamic adaptation of a configuration to a systemenvironment.

As used herein, a “configuration” describes the manner in which acomputer system, device, component, or other element, including anyhardware, software, or both, is set up. A configuration may include, butis not limited to, the system name, the amount of memory available, thenumber of CPUs (central processing units) available, and other relatedinformation. A configuration may be described in various different waysin different settings, and may have a different name or designation incertain environments. To reduce repetitiveness in this description, acomputer system, device, component, or other element may be referred togenerally as a computer system or system. In this description, thecomputer system that receives a configuration may also be referred to asa configuration recipient or configuration consumer.

In an embodiment of the invention, a configuration may be transferredbetween computer systems. For example, when a configuration has beendeveloped for a system that works well for a certain use, that sameconfiguration may be exported to another system that is different thanthe first system. In an embodiment, a configuration may be developed orgenerated for multiple different systems that have differingcharacteristics. In an embodiment of the invention, a configuration isvirtualized for the elements of each system and is adaptable to eachsystem. For example, a software vendor may utilize an embodiment of theinvention to develop a self-adapting configuration together with asoftware product. In this example, the self-adapting configuration maybe shipped together with the product in order to minimize configurationoverhead for the customer.

In an embodiment of the invention, a system configuration utilizesabstract elements that are not dependent on the characteristics of anyparticular system. In an embodiment, the abstract elements of aconfiguration are resolved at run-time to generate values that apply toa particular computer system. As used herein, “abstract” means that anelement has a value to be determined that is not tied to a particularsystem, use, or setting. The value of the element is thus expressed inan abstract fashion, with the value resolvable to a specific value inrelation to a particular system that is assigned to the configuration.

In an embodiment of the invention, a system configuration is dynamic,and the determination of the settings for the configuration is based onthe nature of each computer system and changes that may occur in asystem. A dynamic configuration contrasts with a static configuration ina conventional system, in which the configuration elements need to bemodified to work in a particular system. The elements of a dynamicconfiguration change as the configuration is applied to a system, andmay be modified dynamically as the system is modified in order toreflect current values. Thus, in addition to providing for mobility of aconfiguration, the dynamic values provide for ease in maintenance of theconfiguration because the elements adapt to reflect the current state ofthe system.

In a conventional system, it is not generally possible to copy aconfiguration from one system to another or to generate a configurationthat is usable for multiple different computer systems because of systemdependencies. A conventional system will utilize a static configurationhaving set elements, and a static configuration will not transfer fromone system to another system in the same form as was used in theoriginal system. In conventional operations, it is necessary to manuallymodify each of the system dependent configuration elements to make suchelements match the new system. Further, because of the systemdependencies and the need to create new values for each configuration,there is no assurance in a conventional process that the sameconfiguration will work in the same way in two systems after all of theelements have been set.

In an embodiment of the invention, a configuration is abstracted toeliminate the system dependencies in the configuration. In anembodiment, any system environment dependent settings are removed from aconfiguration database. Instead of static configuration values, aconfiguration introduces dynamic elements to reflect any current system.The dynamic elements may include parameters that characterize eachsystem that receives the configuration. Parameters may include, but arenot limited to, host names, instance names, the number of CPUs, theamount of available memory, and other hardware and software elements. Inan embodiment of the invention, a configuration is dynamic and adaptsitself to the system environment, thereby enabling the movement of theconfiguration from one system environment to another. In an embodiment,the only static settings that may exist in a configuration arenon-system dependent settings that thus are not tied to any particularsystem.

In an embodiment, a configuration element or agent will evaluateabstract configuration elements and substitute the needed values intothe configuration to reflect the characteristics of the system that isreceiving the configuration. In one embodiment of the invention, aconfiguration machine or configuration manager will evaluate theabstract configuration elements and determine the values of theconfiguration elements for the relevant computer system. A configurationmachine or manager may be, for example, an API (application programinterface) that operates on top of a database for a system. In anembodiment, the configuration manager transparently evaluates theconfiguration values at run-time to adapt the configuration to thesystem. However, embodiments of the invention are not limited to anyparticular component, device, or process for the resolution ofconfiguration elements, but rather include any internal or externalagent that can process the configuration elements for a computer system.

In an embodiment of the invention, an abstract configuration may becreated using various different processes. In one embodiment, APImethods of a configuration manager may be used directly to generate theabstract configuration. In another embodiment a specially taggedproperty file, such as a JavaProperty file, may be imported into theconfiguration manager. For example, an enhanced property file may beimported as a property sheet into a configuration database. Othermethods of generating the abstract configuration may be utilized, andembodiments of the invention are not limited to any particulargeneration process.

In an embodiment, system dependencies may include any characteristic ofa system that may be found in a configuration. Dependencies may includesystem identification data, system information such as heap size andnumber of nodes, and hardware availability such as number of CPUs. Eachsystem dependency is expressed in an abstract form in the virtualizedconfiguration in a manner that does not refer to any particular system.The form of the elements in a virtualized configuration may vary indifferent embodiments. For example, system dependencies may includeparameters that are substituted, parameters that require calculation,parameters that rely on or refer to other values, or other types ofdirect or indirect values.

In an embodiment of the invention, system configurations may includevarious default values that are substituted as the values are resolvedfor a particular computer system. In addition, configuration may bedependent on the intended use of a computer system. Various defaults orsettings may be established for different types of uses. The differentuse cases may be addressed in various ways. In one example, templates,forms, or similar devices may be provided to establish certain parametervalues for a configuration.

In an embodiment of the invention, configurations may be structured ordeveloped in multiple levels, with, for example, “higher” levelsproviding default and abstract elements, which are shippable acrosssystem boundaries. In this example, an upper configuration level isapplicable to all systems, but may, for instance, be overridden by lowerlevel configuration levels in certain cases.

In one embodiment, below an upper configuration level may be a usagedefined level, or template level, that provides configuration elementsdesigned for particular use cases. In an embodiment of the invention asystem provides for predefined configurations, which may include the useof templates, forms, or similar devices. The usage defined level mayoverride upper level defaults. In an embodiment, the usage defined levelis based on the system usage and not the particular system and thus theelements remain abstract for purposes of evaluation in conjunction withthe characteristics of the receiving system. The different use casesmay, for example, enable and disable components as needed for theparticular use case. In one possible example, a developer may wish toturn off much of a system, minimizing the number of nodes, to maximizethe system power available to the developer. In another example, a usagecase may require enablement of all server nodes to enable the use of aportal that will carry a large amount of traffic.

In an embodiment of the invention, below the usage defined level may bea system level, which is based on the individual system instance. Thesystem level includes defining the actual system instances belonging tothe system. In an embodiment, each system instance derives itsconfiguration from the template level. The settings received from thetemplate level are abstract and dynamically resolved during runtimeaccording to the given system context, which is attached to the system.Thus, in an embodiment of the invention a configuration is self-adaptingto the particular system environment. In an embodiment, on the systemlevel customizations might be made that are system specific and thuscould be done in a generic or abstract manner on the template level. Thesystem level defines the actual system instances belonging to thesystem. Each system instance derives its configuration from the templatelevel. These derived settings will still be abstract and dynamicallyresolved during runtime according to the given system context, which isattached to the system. Thus, the configuration is self-adapting to theparticular system environment. On the system level customizations mightbe done which are system specific and which could not be done in ageneric (or abstract) way on the system or template level

The system level may further include a custom level above the individualinstance, with the custom level providing customization of theconfiguration for application to a particular site. In an embodiment, anadditional modification may exist between the default level and theusage case level to provide customization that affects all use cases.Thus, customization may be done either for all instances at a higherlevel, or at the individual instance level.

In an embodiment of the invention, a configuration dynamically adapts toa system environment. In an embodiment of the invention, the dynamicadaptation includes obtaining system information for a computer system,storing the system information in a memory for ease of access, andtransparently resolving abstract configuration values based at least inpart on the stored system information.

In an embodiment, a method is provided for applying the systemenvironment, including the system name, Java home (for a Java system),instance ID, hardware present and available, and other such data to thevirtualized configuration. In one embodiment, a process includes takingneeded information from the system environment and using suchinformation in resolution of configuration values. In an embodiment,parameter values of an abstract configuration are mapped to actualvalues determined from the system environment.

In an embodiment of the invention, a system context contains basicparameters that characterize the system, which may include the systemname, the host name, memory, and other items. The system context existsoutside the configuration database, which does not any systemdependencies. System dependencies are abstracted by referencing theparameters from the system context, and the parameters are dynamicallyresolved during runtime.

In an embodiment, certain settings within the configuration database maybe more complex, and may depend on each other. For example, a maxHeapsize depends on a setting for the number of server nodes (e.g.maxheap=memory/number_of nodes.). Further, other settings storedsomewhere else in the database might be dependent on the maxHeap sizeconfiguration. In order to handle these dependencies without redundantconfiguration, value references (value links) are allowed betweendifferent values stored in the configuration database. In order to linkto a value, it is necessary to know the location of the value, whichthus is a dependency on the location of the value to which there shouldbe a link. If the location changes, the link will no longer work. Thus,in an embodiment of the invention system information (which may bedesignated as System_Info) is available. “System_info” provides onespecified location (such as within the configuration database) wherelinks to useful settings (such as number_of_nodes or maxHeap) may bekept. In this manner, components are capable of linking into thespecified system_info configuration, and thus are independent of thephysical location of the setting that is referenced. In an embodiment ofthe invention, there is an advantage because the information there maybe assurance that the data will be in the specified location in thesystem information, whereas there is no such assurance in the internalstructure. In an embodiment, system context contains low level systemparameters, while system information contains the higher levelparameters that may be calculated out of system context parameters, andthat might be of general interest for other component configurations andthus referenced In an embodiment, data that may normally be scatteredthroughout the system structure may provided in a centralized format.

In an embodiment, a process for dynamic adaptation of a systemenvironment includes:

(1) The system context is initialized.

(2) System information is generated to provide links for usefulsettings.

(3) For each parameter in the configuration list, the appropriate valueis obtained from the system environment. The process for obtain suchvalues may vary depending on the type of data that is involved. Forinstance, the process may be broken down into different cases such as:

(a) Pure values that can be obtained from the instance profile. Theseare values that exist in the instance profile generated duringinstallation in the file system

(b) Values that require a combination of values from existing systemvalues. In such a case, the necessary values may be obtained by linkingto the system information. In one example, the full name of an instancemay require the combination of various values that describe theinstance. For instance, a full instance name (which may have a parameter$FULL_INSTANCE_NAME) may be D70_JC20_pcjee01, in which D70 is the systemname, JC20 is the instance name, and pcjee01 is the instance host.

(c) Pure operating system parameters, such as the number of CPU's thatare available and the amount of memory available. These are values thatare determined or limited by the operating system and thus data needs tobe obtained from the OS. For example, if there are more than oneinstance that will be placed in a single box or unit, then the number ofCPUs available for a particular instance is less than the number thatphysically present in the box. In this case, the value returned from theOS may be multiplied by a factor (between 0 and 1) that is configuredwithin the instance profile. In another example, if an instance isvirtualized such that it is spread over multiple boxes, i.e., thehardware for the instance is not limited to a particular physical unit,then the number of CPUs available may be greater than the number presentin a device.

(4) The configuration process continues with resolution of the elementsof the configuration. In an embodiment of the invention, when it is timeto resolve elements of the abstract configuration, each parameter of theconfiguration is isolated and the system context is queried for thenecessary value. In an embodiment, the system information will containthe data needed for the configuration.

In an embodiment of the invention, the system information is stored inmain memory. Main memory is relatively fast, thereby enabling a quickconfiguration process. In an embodiment of the invention, it is onlynecessary to go to the main memory for the system context data. Wheneverthe system is changed, this will be reflected in the system informationstored in main memory.

In an embodiment of the invention, the technical configuration of a Javasystem is simplified through the use of virtualized and adaptiveconfiguration. Embodiments of the invention may be described herein interms of Java objects and processes. However, embodiments of theinvention are not limited to any particular system environment.Embodiments of the invention may be applied to any computer environmentwhich includes the use of a configuration or similar structure with oneor more system dependent elements.

The architectures and methodologies discussed above may be implementedwith various types of computing systems such as an application serverthat includes a Java 2 Enterprise Edition (“J2EE”) server that supportsEnterprise Java Bean (“EJB”) components and EJB containers (at thebusiness layer) and/or Servlets and Java Server Pages (“JSP”) (at thepresentation layer). Other embodiments may be implemented in the contextof various different software platforms including, by way of example,Microsoft.NET, Windows/NT, Microsoft Transaction Server (MTS), theAdvanced Business Application Programming (“ABAP”) platforms developedby SAP AG, and other computer platforms.

FIG. 1 is an illustration of the transfer of a configuration in anembodiment of the invention. In this illustration, a first computersystem (system 1 105) has a particular configuration 115 that is basedat least in part on the system context 120, which includes such elementsas the system name, the instance host name, the number of CPUs, theamount of memory available, and other related system factors.

A second computer system (system 2 110) also contains a configuration125 that is based at least in part on the system context 130 of thesecond system 110. If the configuration 115 of the first system 105 hasbeen developed and would be useful in the second system, then there isan incentive to transfer the configuration 135 and thus to re-use thedevelopment efforts that went into generating the configuration 115.However, in a conventional process, a configuration generally cannot notbe easily copied or transferred because the elements of theconfiguration are based on the specific system context 120 of the firstsystem 105. In order to perform the transfer of the configuration, theresulting configuration 125 for the second system 110 would have to bemodified and corrected to match the system context 130 of the secondsystem 110, which may be a very time consuming process.

In an embodiment of the invention, a configuration is developed as avirtualized, adaptable configuration that is based on abstractconfiguration data, and that does not contain any system dependentelements. In this embodiment, the abstract configuration may be providedto the second system 110. The elements of the abstract configurationwould be resolved based on the system context 130 of the second system130 to form the configuration 125 for the second system 110. In anembodiment, it is possible to transfer 135 an adaptable configuration115 of the first system 105 to the second system 110, or to develop aconfiguration that is usable in both systems. The abstract and adaptablenature of such virtualized configuration allows for transfer withoutfirst making corrections and modifications to the configuration.

In an embodiment of the invention, the transferred configuration 125will be automatically resolved, such as through use of a configurationmachine or engine. The automatic resolution process may include thetransformation of any indirect references, calculated references, andother parameters as needed to match the system context 130 of the secondsystem 110.

FIG. 2 is an illustration of an embodiment of a system for generation ofa configuration. In this illustration, a configuration machine 205 isused to provide a configuration to a consumer of the configuration 215.The consumer may be any component, device, or system that requires aconfiguration for a particular use. In an embodiment of the invention, adatabase includes abstract configuration data 220, the abstract databeing configuration elements that are not tied to any particular system,but rather are adaptable to a system that receives the configuration.For example, the same abstract configuration data may be used inmultiple different systems even though the systems have different systemcharacteristics that require different configuration elements.

In an embodiment of the invention, a configuration machine 205 includesa configuration resolver 210. The configuration machine 205 receives theabstract configuration data 220 and the configuration resolver 210resolves the elements of the abstract configuration data to apply to aparticular system, in this case including the configuration consumer215. The configuration is resolved based at least in part on the systemcontext 225 of the relevant system, which includes relevant dataregarding the particular system 215 that is to receive theconfiguration.

In an embodiment of the invention, a configuration may also be based onthe particular use case intended for the system 230. Thus, theconfiguration may be formed based at least in part on the particular usecase of the configuration consumer 215. The use case may provide certainsystem default elements that are designed for particular uses of asystem.

FIG. 3 is an illustration of an embodiment of configuration development.In an embodiment of the invention, a configuration may be developed inlevels, with upper levels providing defaults that may be overridden inlower levels. In an embodiment of the invention, a configuration mayinherit elements from upper levels. In one example, an engine levelconfiguration 305 may represent a basic default configuration that isnot designed for any particular use or system. The configuration mayinclude abstract elements that are structured as required for aconfiguration engine or machine that will resolve the elements for aparticular system.

In this example, a use-based (or template) configuration level 310 thendefines configurations that are based at least in part on an intendeduse for a system. This level may provide settings that are appropriatefor a particular purpose, which may then be modified as appropriate. Inone example, the use-based configuration level may provide that acertain number of nodes be turned on for the purpose of a particular usecase.

A system level configuration 315 inherits a configuration from theuse-based configuration level. In some instances, the configuration maybe further customized at the system level. The system level defines theactual system instances belonging to the system, with each systeminstance deriving its configuration from the template level. The derivedsettings remain abstract and are dynamically resolved during runtimeaccording to the given system context attached to the system. In thismanner, a configuration is self-adapting to the particular systemenvironment. On the system level, customizations may be implemented thatare system specific, and that could not be accomplished in a generic orabstract manner in an engine level or template level configuration.

FIG. 4 is an illustration of an embodiment of configuration development.In FIG. 4 a particular example of configuration development isdescribed, but embodiments of the invention are not limited to thisparticular structure.

In this illustration, an engine configuration level 405 is illustrated.At this level a configuration engine default configuration is formed420, which provides a basic instance of the configuration. The basicinstance is a virtualized configuration that is abstract and is not tiedto any particular system or used case. In one example, a customizationof the basic instance 425 may be provided, such customization providinga possible modification of all configuration instances for a systemregardless of the particular use of the system.

Also illustrated in FIG. 4 is a use case configuration, the use caseproviding the configuration for various different uses of a system,which are illustrated here as Use Case A 430, Use Case B 435, and UseCase C 440. Each use case provides a template or form for aconfiguration for a particular use of a system. The use caseconfiguration remains an abstract level that is not tied to a particularsystem.

A system configuration is also illustrated, including one or moredifferent configuration instances, such as Instance A 450 and Instance B455. In an embodiment of the invention, the context information for theconfiguration instances will be accessed in the system context. In anembodiment, the system configurations contain information about theinstances that are part of the system, and may further includecustomizations that could not be defined on an abstract level. In thisillustration, the system configuration may also include a customizedinstance 445, which provides customization for instances received forvarious different use cases. In other embodiments, there may be multiplecustomized instances, depending on the particular type of configurationbeing established.

FIG. 5 is a flowchart to illustrate an embodiment of configurationgeneration. In this illustration, a virtualized configuration isdeveloped 505, the virtualized configuration including one or moreabstract elements that are not tied to any particular computer system.In an embodiment, the virtualized configuration is adaptable, with theabstract elements intended to be resolved to reflect appropriate valuesfor a system that is receiving a configuration.

In this illustration, the abstract elements may be stored in a database510, although the process of building up a configuration may vary indifferent embodiments of the invention. A recipient system for theconfiguration is identified 515, and an abstract configuration isprovided for the recipient system 520. A configuration engine or otheragent may be responsible for generating the configuration and resolvingthe abstract elements of the configuration. As a part of this process,the system context is identified for the recipient system 525, whichthus provides the characteristics of the system for purposes ofresolving the configuration elements. A use case may also be identified530, which may be applicable if a form or template is available toestablish a customized configuration.

A virtualized configuration instance is then generated 535. Theconfiguration engine resolves the abstract elements of the configurationinstance for the recipient system 540. In this manner, the configurationadapts to the recipient system, with resolution taking place duringruntime within the recipient system.

FIG. 6 is an illustration of an embodiment of dynamic adaptation of aconfiguration to a system environment. In this illustration, a set ofsystem information 605 contains data obtained from a system structure635 for use in generating a configuration 620.

In an embodiment of the invention, the system information 605 mayinclude, for instance, a max heap size 610 (the heap in general being anarea of memory that is reserved for data created at runtime, and whosesize thus cannot be predetermined) and a number of server nodes for thesystem 615. Numerous other elements may also be included in the systeminformation. In an embodiment, the system information 605 is intended tocontain the data that is needed by the configuration 620.

In an example, the configuration 620 may include a Component 1 625 thatutilizes the max heap size, such as in a calculation, and may include aComponent 2 630 that requires the number of nodes for the system. Inthis example, the max heap size 640 may be present in the deep structureof the system 635, and thus is difficult to locate and retrieve.However, the data has been stored in the system information 605, wherethe data is easily accessible for Component 1 625.

In an embodiment of the invention, the system information 605 is storedin main memory 645. The use of main memory allows quick access to thesystem information, thereby increasing the efficiency of theconfiguration process. However, embodiments of the invention are notlimited to the storage of system context in main memory, but ratherinclude any internal external storage of the system context that isavailable for use for a configuration.

It should be appreciated that reference throughout this specification to“one embodiment” or “an embodiment” means that a particular feature,structure or characteristic described in connection with the embodimentis included in at least one embodiment of the present invention.Therefore, it is emphasized and should be appreciated that two or morereferences to “an embodiment” or “one embodiment” or “an alternativeembodiment” in various portions of this specification are notnecessarily all referring to the same embodiment. Furthermore, theparticular features, structures or characteristics may be combined assuitable in one or more embodiments of the invention.

Similarly, it should be appreciated that in the foregoing description ofexemplary embodiments of the invention, various features of theinvention are sometimes grouped together in a single embodiment, figure,or description thereof for the purpose of streamlining the disclosureaiding in the understanding of one or more of the various inventiveaspects. This method of disclosure, however, is not to be interpreted asreflecting an intention that the claimed invention requires morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive aspects lie in less than allfeatures of a single foregoing disclosed embodiment. Thus, the claimsfollowing the detailed description are hereby expressly incorporatedinto this detailed description, with each claim standing on its own as aseparate embodiment of this invention.

1. A method comprising: receiving a virtual configuration that includesan abstract ent resolvable to a specific element, the receiving beingfrom a first system and performed by a second system, the virtualconfiguration being generated by the first system based on an abstractconfiguration accessed by the first system, on a customization specificto multiple systems that include the second system, and on a use caseapplicable to the second system, the abstract configuration including aset of abstract elements that includes the abstract element resolvableto the specific element, the customization being a version of theabstract configuration, the use case being a version of thecustomization, the specific element corresponding to the second systemand being derivable based on the abstract element and on a systemcontext of the second system; resolving the abstract element to thespecific element by deriving the specific element based on the abstractelement and on the system context of the second system, the resolvingbeing performed by a configuration resolver that is included in aconfiguration machine embodied in the second system; and storing thevirtual configuration in a memory of the second system.
 2. The method ofclaim 1, wherein the resolving of the abstract element to the specificelement occurs at a run-time of a task that is associated with thevirtual configuration.
 3. The method of claim 1, wherein the virtualconfiguration is generated by the first system based on the systemcontext of the second system, the system context of the second systembeing accessible by the first system.
 4. The method of claim 1, whereinthe virtual configuration is generated by the first system based on ause case that is applicable to the second system, the use case being aversion of the abstract configuration and accessible by the firstsystem.
 5. The method of claim 4, wherein the use case includes anumber, the number representing a quantity of nodes to be turned on inaccordance with the use case.
 6. The method of claim 1, wherein thecustomization and the use case are accessible by the first system. 7.The method of claim 1, wherein the resolving of the abstract element tothe specific element includes obtaining a value pertinent to theabstract element from an operating system that is executing on thesecond system.
 8. A system comprising: a memory configured to store avirtual configuration that includes an abstract element resolvable to aspecific element, the virtual configuration being generated by a furthersystem based on an abstract configuration accessed by the furthersystem, on a customization specific to multiple systems that include thesystem, and on a use case applicable to the system, the abstractconfiguration including a set of abstract elements that includes theabstract element resolvable to the specific element, the customizationbeing a version of the abstract configuration, the use case being aversion of the customization, the specific element corresponding to thesystem and being derivable based on the abstract element and on a systemcontext of the system; and a configuration engine configured to: receivethe virtual configuration from the further system; resolve the abstractelement to the specific element by deriving the specific element basedon the abstract element and on the system context of the system; andstore the virtual configuration in the memory.
 9. The system of claim 8,wherein the configuration engine is configured to resolve the abstractelement to the specific element at a run-time of a task that isassociated with the virtual configuration.
 10. The system of claim 8,wherein the virtual configuration is generated by the further systembased on the system context of the system, the system context of thesystem being accessible by the further system.
 11. The system of claim8, wherein the virtual configuration is generated by the further systembased on a use case that is applicable to the system, the use case beinga version of the abstract configuration and accessible by the furthersystem.
 12. The system of claim 11, wherein the use case includes anumber, the number representing a quantity of nodes to be turned on inaccordance with the use case.
 13. The system of claim 8, wherein thecustomization and the use case are accessible by the further system. 14.The system of claim 8, wherein the configuration engine, in resolvingthe abstract element to the specific element, is configured to obtain avalue pertinent to the abstract element from an operating system that isexecuting on the system.
 15. The system of claim 14, wherein theconfiguration engine, in resolving the abstract element to the specificelement, is configured to modify the value obtained from the operatingsystem.
 16. The system of claim 14, wherein the configuration engine, inresolving the abstract element to the specific element, is configured toquery the system context of the system based on the abstract element.